-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Add indexer and str to API documentation #5124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -72,7 +72,12 @@ def upload_prev(ver, doc_root='./'): | |||
if os.system(pdf_cmd): | |||
raise SystemExit('Upload PDF to %s from %s failed' % (ver, doc_root)) | |||
|
|||
|
|||
def build_pandas(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is covered by make doc
already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on windows :-) And it doesn't seem to be in the makefile (at least make doc
has no compile step)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this make it trigger on any attempt to build?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that I know. I simple tried to get the doc build working (cd doc; python make.py html
-> error) and had to C&P from the build_prev
function to the commandline and was fed up after the second time :-) Now its cd doc; python make.py build_pandas; python make.py html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as long as this doesn't cause doc builds to wipe and rebuild pandas, it's fine with me.
Seems like a reasonable (and time-efficient) way to at least document the API. |
really minor note, can you fix the typo in your commit message: convinience --> convenience? Not a big deal, just would be nice. |
done |
@@ -419,8 +425,46 @@ Time series-related | |||
Series.tz_convert | |||
Series.tz_localize | |||
|
|||
String handling | |||
~~~~~~~~~~~~~~~~~~~ | |||
``Series.str`` can be used to access the values of the series as strings and apply several methods to it. Due to implementation details the methods show up here as methods of the ``StringMethods`` class. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we stick to the 79 chars line length? (or at least to 99 chars) Because now it is difficult to read in the source code (for example on github, it doesn't fit on my screen).
Is there a convention in pandas to follow or not follow pep8 on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you're adding something new to the docs, generally should keep to 79 characters
@JanSchulz It is always good to add more docs to the api docs! (there are still missing a lot). Regarding building the (api) docs on windows, I have the same problem with the io.rst. I always remove that part in io.rst when developing/building the docs locally .. (which is a little bit annoying). |
@JanSchulz while you are adding....can you put in |
Wow, there is quite a lot of API documentation missing: |
you seem to be double counting the undocumented, e.g. |
@jreback That's because the API documentation refers to the context |
@jreback: to_timedelta added @jorisvandenbossche, @jtratner: shortend the lines Sorry for the rebase mess :-( Not sure how to convince github that the PR now starts at a different commit :-( |
force push the branch. Also, just a heads up, some of the methods you point out are quasi-internal (like |
@jreback re double counting: I removed more or less all context from api.rst (which resulted in only two errors: one for Stata*: #5144 and one for sql read_frame/ write_frame). The resulting count: public methods: 983; documented: 503, undocumented: 522 @jtratner done: https://github.com/pydata/pandas/wiki/Undocumented-public-functions I also updated the ipynb to the version I used to generate this data (you also must change api.rst so that all context point directly to pandas and not to modules like pandas.io.sql) |
can you do that for the rest of the pandas docs? |
See also #4790. If eg |
@JanSchulz pls rebase on master |
@JanSchulz can you rebase and squash? |
@jreback done (hopefully...) |
@JanSchulz Did you rebase? Because it seems that your commit on api.rst has not included the changes of eg #5208 (although I don't think it would conflict) |
can you add the indexeras (iat/iloc/loc...etc) to Panel as well? |
Not sure why it didn't pick up the new changes, but this seems to include them. |
@jtratner What do you want for the rest of the documentation? As I understood the docs, the rest does not have links to the API documentation (see e.g. http://pandas.pydata.org/pandas-docs/dev/groupby.html) |
@JanSchulz this looks fine.... should we include and not sure we actually have explicitydocs on it |
@JanSchulz this looks fine @jorisvandenbossche @jtratner merge? |
@jreback certainly fine! |
@jreback @jorisvandenbossche rebased and removed some trailing whitespace |
@jorisvandenbossche pls give a once over..looks mergeable to me |
@jreback good to merge! |
Add indexer and str to API documentation
closes #5068